Description

The class packages/core/src/secp256k1/Secp256k1.ts unifies any reference to SECP256K1 functionalities, constants and methods. Albeit the class is made of static methods, this approach simplifies name space conflicts with 3rd parties libraries exporting secp256k1 constants and it is coherent with the OOP paradigm adopted in the SDK.

The examples and documentation are reviewed, the docs/diagrams/architecture/secp256k1.md file documents the class.

Code documentation reports precisely the noble/scure use of cryptographic sensitive algorithms and the fall-back to global.crypto for the runtime throwing exceptions.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected) limited to renamed references.
• This change requires a documentation update: done.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• yarn test:examples
• yarn test:solo
• yarn test:unit

Test Configuration:

• Node.js Version: v20.14.0
• Yarn Version: 1.22.22

Checklist:

• My code follows the coding standards of this project
• I have performed a self-review of my code
• I have commented on my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• New and existing integration tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have not added any vulnerable dependencies to my code